JPH07121359A - Method and device for preparing program and method and device for preparing printed image data - Google Patents

Abstract

PURPOSE:To easily prepare printing images for which a printing position or the like is surely accurate without errors by checking the consistency of data based on the attribute, digit number and record layout of transaction data. CONSTITUTION:When the start processing of a main program is completed after supplying a power source, a controller 1 displays the main menus of a specification editing processing, a job processing and completion at a display device 3. In this case, the specification editing processing menu performs the editing processing of the input of the specification contents of the transaction data and a printing out position or the like and the job processing menu checks the transaction data, automatically generates a code conversion program and prepares printed image data based on specifications determined by the specification editing processing menu. Then, since the consistency of the transaction data is checked based on the information of the record layout, data attribute and digit number of the transaction data, defective parts can be discovered and corrected before conversion.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for creating print image data by inputting a data string to be printed on an output paper such as a form into a printer and editing it in a format that can be printed out on the output paper. Regarding the device.

[0002] Conventionally, when a predetermined data is printed on an output paper such as a pre-printed material having a predetermined form or a blank sheet, an invoice or a monthly report is prepared, first, an individual customer list, sales amount, etc. Data to be printed on the output paper is extracted from the master file, which is a data file, and collected into a record that is a unit of data (corresponding to the data described on one invoice), and the records are collected in a specified number. Create a file commonly called a transaction file. Next, for each data of the record written in this transaction file, determine the print position according to the format to be printed on the output paper, add line feeds, blanks, etc. according to the printer to be used, and print image data ( A PIT (also called a print image tape), which is called a PID because a magnetic tape is usually used as a recording medium, is created. And this PI
It is general to set an output paper for outputting D as a printer and perform a printing process.

For example, a case will be described as an example in which a bill is created on an output sheet of a predetermined form. FIG. 25 is a diagram showing the processing steps in the case of creating an invoice on the output paper of a predetermined form. In FIG. 25, first, predetermined data is extracted for each individual customer from the customer database in which the address, name, etc. of the customer to whom the invoice should be sent are recorded, and the transaction database in which the transaction details and the billing amount are recorded. Then, a transaction file is created by collecting the records into records and collecting records corresponding to all predetermined customers (STEP 1). Next, the print position of each data forming the record is determined according to the output paper to be printed, and the PID is created according to the print output image including the line feed code, the blank code, etc. (STEP 2). Then, by setting the PID and the output paper to be output in the printer and performing printer output processing, it is possible to create a bill in which predetermined data is printed at a predetermined position (STEP 3).

Here, the PID creating process will be described. FIG. 26
FIG. 4 is a diagram showing one record written in a transaction file. As shown in FIG. 26, it is assumed to be composed of three fields. Here, one record is composed of data printed on one output sheet. The field indicates an area in which data is written, and one field or more data is written in one field. Then, records of the configuration shown in FIG. 26 are written in the transaction file for the number of output processing cases. The order of the fields forming the record may be arranged independently of the form of the output paper.

Further, FIG. 27 is a diagram showing specifications relating to printing positions and the like when printing is performed on output paper. These transaction data are supposed to be printed on the output paper of a predetermined form as shown in FIG. That is, the data “name” recorded in the field 1 is the 11th in the 5th line.
The data "address" printed in the second to tenth digits and recorded in the field 2 is printed in the first to tenth digits in the second line, and the data "billing amount" recorded in the field 3 is the fifth.
It should be printed in columns 31-35 of the line. Note that the output paper portion is omitted in FIG. The number of digits is a value in the case where 1-byte data such as alphanumeric characters is expressed. Therefore, in 2-byte data such as Japanese, one character is expressed by 2 digits.

In such a case, it is obvious that each data will not be printed at the correct position to be printed by simply setting the transaction data and the output paper on the printer, and each data should be printed on the output paper. In order to print correctly at the position, it is necessary to change the format of the transaction data record to the data format shown in FIG. FIG. 28 is an example of PID. FIG. 28
According to the data format shown in, the printer reads one record, first page breaks, and then takes in the next output sheet. The first line is a line feed, the second line is the first 10 digits, and the 11th digit is blank. Print the contents of the field 2 "address" in the 40th to 40th columns and start a line feed. Then, after the 3rd and 4th lines are fed back, the 5th line is blanked in the first 10 columns. Print the contents of field 1 "Name" in the 20th digit, leave the following 10 digits blank, and
The contents of field 3 "billing amount" are printed at the 1st to 35th digits and a line feed is performed. This series of data strings are arranged for the number of output cases. The Kanji IN code in FIG. 29 is a code indicating that the following data is data of 1 character and 2 bytes, and the Kanji OUT code is a code indicating the end of data of 1 character and 2 bytes.

In this way, transaction data as shown in FIG. 26 is output as shown in FIG.
The PID creation process is to change the format to that shown in Fig. 8 so that the printer can read it and print each data at the position where it should be printed.
Is created.

[0008]

However, in the transaction data presented by the customer in the consignment processing, there is a case where a code having a data attribute according to the specifications is not stored and defective data exists. If the above PID conversion processing is performed on such transaction data, defective data exists in the PID, and a print output error occurs due to a defective code. Therefore, it takes a lot of time to find the defective part of the cord, and the output efficiency is lowered. Also, in the conventional PID creation process, a program in a programming language such as C language or COBOL must be created each time considering the print format of the output product and the specifications of each printer to be used. Was very laborious and costly. Furthermore, since these created PID creation programs could only be used uniquely within each model, it is virtually impossible to operate on a different model or on a lower model even if the number of processes is small. It was

The present invention is intended to solve the above-mentioned problems, and anyone can easily and reliably make a mistake in the print position, print content, etc. on the output paper without performing the complicated work of creating a program. It is an object of the present invention to provide a method and an apparatus capable of creating a print image without a mark.

[0010]

The above object can be achieved by the present invention described below. That is, (Claim 1) Automatic check program generation processing for automatically generating a check program for checking the consistency of transaction data based on the information such as record layout, data attribute, and number of digits of transaction data which is the original data of print image data. A method for creating print image data, characterized by performing the following. (Claim 2) A print image data creating method, wherein a check process for checking the transaction data is performed by the check program generated by the check program automatic generation process according to claim 1. (Claim 3) A method of creating print image data, characterized in that the consistency of the transaction data is checked based on the record layout, data attribute, and digit number information of the transaction data which is the original data of the print image data. (Claim 4) A storage device in which transaction data, which is original data of print image data, is stored,
An input device to which the record layout, data attribute, and the number of digits of the transaction data are input, and a check program automatic for automatically generating a check program for checking the consistency of the transaction data based on the information input to the input device. A program generation device comprising: a control device having a generation means. (Claim 5) A print image data creation device, wherein the control device has a check means for checking the transaction data by the check program generated by the program generation device according to claim 4. (Claim 6) A storage device in which transaction data, which is original data of print image data, is stored,
The control device has an input device for inputting information on the record layout, data attributes, and the number of digits of the transaction data, and checking means for checking the consistency of the transaction data based on the information input to the input device. A print image data creation device characterized by.

[0011]

Operation: Print image data (PID as described above
To check the consistency of the transaction data based on the record layout, data attributes, and the number of digits information of the transaction data that is the original data for creating the transaction data before converting the transaction data to print image data. You can find defects and fix them. Further, since the check program for checking the consistency of transaction data is automatically generated, the device for automatically generating the check program and the device for executing the check program may be the same device or different devices. Since the range of selection of devices is large and distributed processing is possible, it is possible to efficiently perform time-consuming data consistency check.

[0012]

The present invention will be described below based on the preferred embodiments. FIG. 1 is a diagram showing an example of a system configuration for implementing a PID creating method and apparatus according to the present invention. In FIG. 1, reference numeral 1 is a control device including an arithmetic processing unit such as a microprocessor and peripheral circuits, that is, a main body such as a personal computer or an engineering workstation, 2 is an input device such as a keyboard or mouse, and 3 is a color CRT display device. Such as a display device, 4 a floppy disk storage device (referred to as an FD device), 5 a magnetic tape storage device (referred to as an MT device), 6 a storage device capable of storing a large amount of data such as a hard disk, and 7 a printer. , 8 are networks, and a local area network (called LAN) such as Ethernet can be used.

FIG. 2 is a diagram illustrating a record of transaction data, FIG. 3 is a diagram illustrating a print layout, and FIG. 4 is a diagram illustrating data of one cycle of PID. Next, an outline of the PID creating method and apparatus of the present invention will be described by taking the case of creating the PID of FIG. 4 from the transaction data of FIG. 2 in the print layout of FIG. 3 as an example.

FIG. 5 is a flow chart showing the entire processing executed by the control device 1. When the start-up process of the main program after power-on is completed, the control device 1 displays the main menu on the display device 3 ( S1). There are 3 main menus: "specified editing process", "business process", and "end".
It is a menu. Here, the designated edit processing menu is a menu for performing edit processing such as management information related to printout work, input of specifications of the transaction data MT, creation of a new external character, printout position, and the like. That is, the specifications of the data exemplified in FIGS. 2 and 3 are input to enter the PI.
This is a menu for creating a data file required for automatic generation of a D conversion program. Then, the business processing menu checks transaction data and automatically generates a code conversion program, and the PI as illustrated in FIG. 4 is based on the specifications defined in the designated editing processing menu.
This is a menu mainly for creating D. The end menu is a menu for ending the main program.

With the main menu displayed,
When one of the main menus is selected by placing a pointing point on the menu and pressing a key on the keyboard, a button of a mouse or the like (S2), the selected subprogram is launched (S3 to S5). As an example, when the business process menu is selected (S2), the business process starts (S2).
4), the sub menu is displayed on the display device 3. The submenus are three menus of "PID formation", "backup / registration", and "business ID (identity) confirmation".

As described above, the PID formation menu is a menu for creating a PID by generating a check and code conversion program and a PID conversion program based on the data file created by the designated edit processing menu. The backup / registration menu is the PI of the present invention.
Used when the MT device 4 is used to transfer various data files used in the D creation method to the MT, or when the data transferred to the MT is loaded to the hard disk storage device 6. It is a menu to do. The business ID confirmation menu is a menu used when confirming whether or not a corresponding ID exists. When one of these menus is selected (S7), the subprogram of that menu is started up (S8 to S10) and the processing is performed. Next, the details of the above PID editing method of the present invention will be described in the order of “designated editing processing”, “PID formation”, and “backup / registration”.

(Designated Editing Process) FIG. 6 is a flowchart showing the designated editing process in the designated editing process (S3) of FIG. First, the operator inputs the business ID (S2
1). Then, the system determines whether or not the corresponding ID is registered (S22). Here, the system includes the hardware configuration of the system illustrated in FIG. 1 and FIG.
The software configuration of the system illustrated in (1) and peripheral related systems (not shown) are included. FIG. 6 is a flow chart showing a designated editing process when the corresponding ID is not registered. The case where the ID is registered will be described later with reference to FIG.

If the corresponding ID is not registered in FIG. 6, management information is input (S23). FIG. 8 is a diagram showing a management information input screen displayed on the display device 3. In FIG. 8, the “registration date” is the date when the PID was created in the consignment processing business. The "order number" is for displaying the preprint data of the form block making CAD on the screen based on this number. "Business ID" is
It is a number that manages the system data file. The "creator" is the person who created the PID in the system. If there is "pre-print data", the ruled lines (characters) are drawn on the X window based on the data of the form work sheet CAD. If not, the screen of the pre-print section is not displayed and the screen is displayed. Displays the spacing chart. However, in either case, the form size and the number of pitches per inch are input. "Printer model" sets the printer model corresponding to the PID created by the system. The above management information data is input by the operator from the keyboard, mouse, etc. while looking at the screen of FIG.

When the management information is input (S23) in FIG. 6, transaction data MT specifications are input (S24). FIG. 9 is a diagram showing an input screen for the transaction data MT specifications displayed on the display device 3. In FIG. 9, "label designation" is performed by selecting NL or SL. NL means non-label,
SL means a standard label. Select "single" or "multi" for "volume configuration". Single means that MT has one volume, and multi means that MT has multiple volumes. Therefore, if you select multi, enter the "number of turns". "1 byte code" is ASC
II, EBCDIC, or none is selected. ASC
II and EBCDIC mean that the codes of the characters specified by 1 byte are ASCII code and EBCDIC code, respectively. No means that there is no 1-byte code character. "2-byte code" is JE
F, IBM, JIPS-E, JIPS-J, Shift JI
Select either S or nothing. These mean that the code of the character specified by 2 bytes is each code. For “external character code”, select “yes” or “no” depending on the presence or absence of the external character code. If there is an external character code, create an external character code correspondence table with an editor. FIG. 10 is an input screen of the editor displayed on the display device 3. The above-mentioned transaction data MT specification data is input by the operator from the keyboard, mouse or the like while looking at the screens of FIGS.

In FIG. 6, transaction data MT
After the specification input (S24) is completed, the presence / absence of the external character font is next determined (S25). If the external character font is present, a new external character font is created (S26) and then the record field data specification input (S27) is performed. If there is no external character font, the process directly proceeds to S27. FIG. 11 shows the display device 3.
It is a figure which shows the input screen of external character font new creation (S26) displayed on FIG. In FIG. 11, the filled portion in the large frame represents the shape of the external character font, and the shape can be input from the keyboard, mouse or the like while looking at the screen of FIG. Further, it is possible to search and use a desired external character font from existing font data, external character data of CAD for creating a form block, or to modify it to obtain a desired external character font.

In FIG. 6, a new external character font is created (S2
When 6) is completed, the data specification of the record field illustrated in FIG. 2 is input (S27). FIG. 12 is a diagram showing an input screen for the data specifications of the record fields displayed on the display device 3. In FIG. 12, the “column position start point” is numerical data indicating the byte position of the record of the transaction data at which the start position of each field is, and the “attribute” is the attribute of the data. ANK (alphanumeric katakana), packed / unpacked type (number), with signature (plus / minus in the case of numbers), etc. can be selected. In FIG. 12, 9 indicates that the field data is a numeral, N indicates a Japanese character (2-byte character), and X indicates that it is composed of an alphabet and a numeral. "Number of digits" indicates how many numbers, alphabets and Japanese characters are present in the field. The “field name” is the name of the field, and can be substituted for the variable name of the check program and the variable name of the PID conversion program. Although not shown in FIG. 12, a “comment” explaining each field can be added. This comment facilitates debugging and maintenance when the generated program is used for other purposes.

The above record field specification data is input by the operator from the keyboard, mouse or the like while looking at the screen of FIG. When "Save" in FIG. 12 is selected when the input is completed, the input record field specification data is saved in the transaction data MT specification file.

In FIG. 6, when the data specification of the record field (S27) is completed, the spacing chart is displayed next (S28). FIG. 13 is a diagram showing a display screen of the spacing chart displayed on the display device 3. In FIG. 13, when there is the data of the form copy making CAD, a predetermined spacing chart is displayed on the screen according to the chart classification in the data. When there is no CAD data for creating a form copy, a predetermined spacing chart given as a default is displayed on the screen. Changes are made if the defaults are determined to be inappropriate. If there is data for the form copy preparation CAD, a predetermined spacing chart is displayed on the screen, and then the ruled line frame created by the form copy preparation CAD is displayed. FIG. 14 is a diagram showing a display screen of the ruled line frame displayed on the display device 3. Further, a judgment is made as to whether or not to display the pre-printed portion characters created by the form copy making CAD. Enter Y to display characters, enter N to not display characters.

When the display of the spacing chart (S28) is finished in FIG. 6, the printout specification is next input (S29). FIG. 15 is a view showing a printout specification input screen displayed on the display device 3. Figure 15
In the upper left, the spacing chart, ruled line frame, and pre-printed portion characters are displayed in the upper left. Also in the center,
The field layout is displayed. On the right side and the lower side, a plurality of menus of operations performed on the printout specification input screen are displayed.

The above menu will be described. "letter"
Is displayed when the field layout is not displayed in the window of the display screen and is erased when the field layout is displayed in the window of the display screen by placing the mouse pointing point on this and pressing the mouse button (called hit or select) . “Paste” hits the field number to select the designated character string based on the printout specifications, determines the coordinate position, and after editing processing, hits this to determine the paste position. "Change number of points" is a menu to be specified when changing the size of pasted characters. For single-byte characters, the default is 10 cpi (character per inc
h) In the case of 2-byte characters, the default is set to 9 points (points), and when pasting at other points, hit this and select a prescribed character size.

"Hyphen edit" hits this menu when it is necessary to add "-" when outputting a zip code or sequence number. For example, 9999-99, X-99
999999 etc. For example, "△ -sama" hits this menu when a space "" is added between the name and the name, the name and the hall, and the name and the middle. "1B → 2B" is 1
Hit this menu when converting the characters set in bytecode to 2-byte code and outputting.
“Calculation” hits this menu to specify the calculation formula and the number of digits when calculating the total etc of the usage amount. "Left Alignment" selects this menu and sets the number of characters per line when you want to break the address and message text.
"Flag determination" includes a flag in the transaction data, and it is determined by the flag value, and when it is desired to output different contents to the same position, this menu is hit. Create a correspondence table between flag values and field numbers or message texts.

The "fixed character string" has no data in the transaction data, but when printing out as fixed information, this menu is selected and the necessary character string is registered.
For example, 〒, Mr., message text, etc. "End" saves the information about the contents when the printout specifications are input. “Pick” is for the character string once decided, and when you want to change it, select this menu and correct it. For "Cursor designation", select this menu if you want to enter the paste position using coordinate values. "Change line spacing" is selected when you want to change the number of pitches (line spacing) per inch of the displayed spacing chart. "Enlarge" selects this menu and specifies the area when enlarging the screen display of each window.
“Standard”: Select this menu if you want to return the screen display of each window from the enlarged display to the standard display state.
"Clear" selects this menu when you want to clear (delete at all) the character string specified by the pick.

For "imposition", this menu is selected when performing multi-imposition processing (copy & paste) at the time when the printout specifications have been input for one form. After designating the copy area, the sequence is designated to determine the read record position information. "Encryption" hits this menu when you want to apply encryption processing to the character string whose paste position has been determined. “Sequence No.” selects a sequence number pattern and pastes it. Next is EXI
T? When no is selected in (S30), the process returns to the task ID input (S41). If yes is selected, the screen returns to the main menu display (S1) of the main program shown in FIG.

FIG. 7 is a flow chart showing the processing steps when there is a corresponding business ID in the determination (S22) of whether the business ID of FIG. 6 is registered. In this case, the designated editing process should have been completed for the time being, so the main purpose is to correct the specification or to designate the unedited portion. 7 and 6 differ in this respect,
Items without work can be skipped and skipped, and necessary work items can be selected directly, and the work can be performed immediately.
In FIG. 7, the business ID input (S21) and the presence / absence determination (S21) of the business ID are the same as those in FIG. 6, but the determination result is that the corresponding business ID exists in the system. Therefore, the specification content correction menu is displayed on the display device 3 (S31). This menu is "Management Information", "Transaction Data M
There are five types, "T specification", "new character font creation", "record field specification", and "printout specification".

When "management information" is selected with the specification correction menu displayed on the display device 3 (S32),
The operation can be started from the management information input (S23) in FIG. 6 (S33). "Transaction data M
When "T specification" is selected (S32), the operation can be started from the transaction data MT specification input (S24) in FIG. 6 (S34). When "New character font new creation" is selected (S32), the operation can be started from new character font new creation (S26) in FIG. 6 (S35). When "Record field specification" is selected (S32), the work can be started from the data specification input of the record field specification (S27) in FIG. 6 (S36). When "printout specification" is selected (S32), printout specification input (S
The work can be started from 29) (S37). EXIT? When no is selected in (S38), the process returns to the task ID input (S21). If yes is selected, the screen returns to the main menu display (S1) of the main program shown in FIG. This is the end of the description of the designated editing process shown in FIGS. Next, PID formation will be described.

(PID formation) FIG. 16 is a flow chart showing a conversion processing method in PID formation (S8) which is a submenu of the work processing (S4) of FIG. First, the operator inputs a work ID (S41). Then the ID
Management file corresponding to, transaction data MT
The system determines whether a specification file, a record field specification file, a fixed information file, a printout specification file, etc. exist (S42). Here, the management file is created by the management information input (S23) of FIG. 6, the transaction data MT specification file is created by the transaction data MT specification input (S24) of FIG. 6, and the record field specification file is the record field of FIG. 6 is created by the data specification input (S27), and the fixed information file and the printout specification file are files created by the printout specification input (S29) of FIG.

For example, FIG. 18 shows an example of a record field specification file when the record layout is shown in FIG. In Figure 18, from .start.: Header to .end.: Header
The total number of fields is recorded in the number up to, and the information entered respectively between .start.: Body and .end.: Body below that is recorded. label is a field name, which corresponds to a variable name in generating a program. comment is just a comment for the field, and input items are provided so that the contents of the field can be easily clarified when correcting. Kind indicates an attribute related to field data, and this attribute item serves as a criterion for determining whether the data code in the field is correct. start records the number of bytes at the start position of the field in each record, and matches the number of bytes to start checking at the time of checking. length indicates the data length of each field. This is also the same as the data length to be checked at the time of checking as in start.

FIG. 19 shows an example of a fixed information file, which is generated when the menu "fixed character" is selected and executed in the printout specification input (S29) of FIG. The fixed information file in FIG. 19 is .start.: Head.
The number of all fields is recorded in number between er and .end.: header, and the information entered respectively between .start.: body and .end.: body below that is recorded. constant indicates a character string set as fixed information. The character code set here is recorded with the character code supported by the printer. Therefore, when the character code used in the control device 1 and the character code supported by the printer are different, code conversion is performed. kind shows the attribute of the character string set by constant, and label becomes the variable name when generating a program. Kind and label are automatically generated from the contents set with constant, so ANK from a menu
It may be divided into two, Japanese and Japanese.
It may be generated by judging from the character code set in nt. Since the variable name must be unique for label, it is generated by combining the number of cases registered with constant with a sequential number.

FIG. 20 shows an example of a printout specification file when the printout specification is that shown in FIG. Figure 20
At, between .start.: Header and .end.: Header
Record the total number of layouts in number, and .start .:
The information entered between body and .end.: body is recorded. unit represents the unit of the coordinate system that sets the output position, and has a unit system of columns, inches, and dots in the horizontal direction. x and y record numerical values based on the unit of unit. For length, record the character string length at the time of output with the number of digits. The kind indicates the existence location of the original data necessary for output. Whether the original data is a transaction data file, a fixed information file, or another file is identified by this value when the PID is generated. I know where to read the data from. label is the label for the data selected when designing the printout, and it has the same contents as the label determined in the record field specification file and the fixed information file specified earlier. size indicates the character size set at the time of output.

The description of the file is finished here, and FIG.
Returning to S41, the description of PID formation is continued. If these files do not exist, an error message is displayed on the screen of the display device 3. The file name or the like that does not exist as an error message. On the error message screen, a display for selecting whether or not to continue the PID formation is displayed. When selecting to continue, EXIT? (S54)
Since no was selected in, enter the business ID (S
Return to 41). If you select NO, EXIT? (S5
It means that yes is selected in 4), and the process returns to the main menu display (S1) of the main program in FIG.

If these files exist, the transaction data is read (S44). This is the "label" in the transaction data MT specification file,
Reading is performed with reference to the items "volume", "record length", "recording density", and "block length". In the case of multi-volume, the files are linked together to create a work file for checking and code conversion processing. Also, the device name for creating the PID and the printer name for outputting are selected and input. The following processing contents differ depending on this selection.

Next, a check and code conversion program is automatically generated (S45). This automatic generation is performed by using the code generator to generate a program code from the transaction data MT specification file and the record field specification file. The program generated at this time is a source program such as C language or COBOL, and when the program is executed,
Load modules can be created by compiling and linking depending on the processing device, and any device can be selected. If the data code of transaction data does not require code conversion, only the check program is automatically generated. After the check and conversion program is generated, it is determined whether the control device 1 uses the previously selected PID creation device name or PID creation is performed using another model. When outputting with another model, transfer the check and conversion program over the network, or
It is possible to output to a recording device such as an FD device or an MT device. Further, in the automatic generation of the check and code conversion program (S45), it is sufficient to automatically generate the program as needed, such as when the check or the code conversion is performed by another model, and when the program is not automatically generated, It can be checked by the process (check process) described later.

Next, check and code conversion processing is performed (S46). The transaction data file fetched in S44 is used as a work file, the program automatically generated in S45 is activated, and the above process (S46) is performed.
It is determined whether or not there is an error in the check (S47), and if there is an error, a code error file is created (S48). The contents of this code error file are verified, the transaction data is corrected (S49), and the transaction data is read again (S49).
Go back to 44) and try again. In the check, it is determined whether or not there is an error (S47), and if there is no error, a code-converted master data file is created (S50). The total number of bytes of print data per page of PID to be output is calculated from the printout specification file, and the code-converted master data file is divided so that the hard disk storage device 6 does not overflow when the PID data is stored. A divided master data file is used during PID conversion.

Next, a PID conversion program is automatically generated (S52). This automatic generation is based on transaction data MT specification file, record field specification file,
This is performed by generating a program code from a printout specification file, print information data, and external character font data using a code generator. The program generated at this time is, for example, C language, COBOL
Source program such as, when executing the program, can be compiled according to the processing device,
Any device Further, the character code of the PID to be output is unified, for example, EBCDIC, JEF code, or the like. After the PID conversion program is automatically generated, the PID creation device name previously selected is used for PID by this control device 1.
It is determined whether the conversion process is performed or another model is used. When outputting with another model, transfer the PID conversion program via the network, or
It is possible to output to a recording device such as an FD device or an MT device. Further, in the automatic generation of the PID conversion program (S52), the program may be automatically generated as necessary when the conversion to the PID is performed by another model,
If the program is not automatically generated, the process (P
ID conversion processing).

Next, the PID conversion program automatically generated in S52 is activated to create a PID (S53). When the control device 1 performs the PID conversion processing, the PID conversion program previously generated is automatically compiled,
After linking and creating the execution module, the execution module can be executed to create the PID suitable for the output printer device. The output MT displays a page serial number range as a message for each volume. EXIT? When no is selected in (S54), the process returns to the business ID input (S41). If yes is selected, the screen returns to the main menu display (S1) of the main program shown in FIG. This is the end of the description of PID formation. Next, backup / registration will be described.

(Backup / Registration) FIG. 17 is a flowchart showing the processing steps in the backup / registration (S9) which is a submenu of the job processing (S4) in FIG. In FIG. 17, the backup and registration menus are displayed (S61) and one is selected (S62). Select Backup if you want to save the data files generated by this system, and select Register if you want to reuse the data files backed up by this system.
When backup is selected (S63), the business ID and data file name currently saved by the main program process of FIG. 5 are displayed (S64). When the business ID is selected, the data file is saved in MT (S6
5) Further, information on which data is stored in which MT is stored in the MT storage status file (S66).
EXIT? When no is selected in (S67), the display returns to the menu display (S61). If yes is selected, the main menu display (S
Return to 1).

When registration is selected (S68), the business ID to be registered is input (S69). The MT storage status file is searched (S70), and the MT in which the data file relating to the input business ID is stored is displayed (S71). The corresponding MT is set in the magnetic tape device (S72), and the data file is registered in the system side (S73). EXIT? When no is selected in (S67), the display returns to the menu display (S61). If yes is selected, the screen returns to the main menu display (S1) of the main program shown in FIG. This completes the description of backup / registration. Next, "check processing", "check program generation", and "P" which are characteristic parts of the present invention
A more detailed description of "ID conversion processing" and "PID conversion program generation" will be given in this order.

(Check Processing) FIG. 21 is a flow chart for explaining the transaction data check processing. In FIG. 21, first, the code name of the transaction data that is the input data (JIS, ASCII,
JEF, IBM, etc.) is read in both 1-byte and 2-byte systems (S81). Next, the external character code value set in the transaction data is read. The external character code is normally read even if it exists outside the regular code area because it is registered in a different file, etc., and therefore is processed differently from the above code (S82). Then, the record layout for one record of the transaction data input earlier is read from the record field specification file. When the check program is not generated, it is not necessary to read the field name and comment contents (repeated by the number of fields). At this time, the total number of transactions processed and the record length are read (S83).

After reading the record layout, discrimination processing is performed based on the data type of each field (S84).
The X item indicates the entire 1-byte character, the 9 item indicates numerical data, and the N item indicates the entire 2-byte Japanese character. Next, a check (S85) is performed, and the processing process will be described by taking the X item as an example. The transaction data for the number of digits is read from the leading position of each field that has been read previously (S86), and it is determined from the input code name whether it is within the normal range of the code table for the X item (S8).
7). At this time, the code value of the read external character is not considered as a check target. When it is determined that the input code is within the normal range of the code table, the next code value is processed and repeated for the number of digits. If the input code is determined to be within the normal range of the code table, the error content is recorded (S88). For example, if the input transaction data is ASCII code 00 (H), it is determined that an error occurs because the character is not defined. At this time, the byte position in the transaction data where the error occurred, the code value 00 (H)
In the error file. Check processing is similarly performed for other data items.

(Automatic Check Program Generation) FIG. 22 is a flow chart for explaining automatic check program generation of transaction data. In FIG. 22, first, read the code name of transaction data,
It will be used as a judgment material for importing the check library. Further, the total number of transactions processed and the record length are read (S91). Next, the external character code value set in the transaction data is read (S9
2). Next, the record layout information regarding the first field is read. In this case, the field name (variable name) for generating the program must be read.
Comments (used for debugging, maintenance, etc.) may be read because they relate to the appearance of the source program, or may not be read if not necessary (S93,
S94). And the read field name, start position,
A program for reading the first field data is created according to the number of digits (S95). After that, the attribute of the data and the input code name are determined, and each library name describing the check range in advance is described in a program (S96). Repeat these for the number of fields,
A main function part is created (S93). Finally, for the check library, create a program control statement that uses the external character code value and excludes this value from the check.

(PID conversion process) FIG. 23 is a flow chart showing the PID conversion process. In FIG. 23, first,
The name of the output printer is read, and how to convert the PID output format is determined (S101).
Next, the parameters set for the first field of the printout specification file are read. The parameters to be read here are the unit of output start coordinates, the coordinate value in the horizontal direction, the number of output digits, the character size, the file identifier of the input data (transaction data, fixed character string data, etc.), the field name of the input data. Exists (S102, S103). Set the control code for the line from the name of the output printer or, in the case of a line printer, from the output start position coordinates. If it is not a line printer but a printer capable of addressing all points, it is not necessary to set the line control code (S104,
S105).

Next, the character size is set (S
106). Then, it is determined whether the input data is transaction data or fixed character string data from the identifier related to the input data of the record field specification file (S107). After the discrimination, the input data is read using the start position and the number of digits of the record field specification file. At this time, read the record field specification file or the attributes of the fixed character string data (S
108), using the attribute, it is determined whether the input data is X, 9 items or N items (S109).
According to this determination, when converting to PID, the shift code is not added to the data when reading ANK (S11).
0), in the case of reading Japanese (S111), the shift code is added to the data (S112). The above process is performed for each field in the printout specification file (S102, S114), and output as a PID at any time (S113).

(Automatic Generation of PID Conversion Program) FIG. 24
FIG. 7 is a flowchart showing a PID conversion program automatic generation process. In FIG. 24, first, the field name (variable name) of the input data (transaction data, fixed character string data, etc.) defined in the printout specification file and the file existence identifier of the input data are read,
The variable name of the input data in the PID conversion program and the data reading unit are generated (S121, S122, S1).
23). The i-th parameter (coordinate unit, output start coordinate value, input data field name, input data file existence identifier, output digit number, character size) in the printout specification file is read (S124, S125). In the case of a line printer, it is necessary to generate a line control code from coordinate values in the vertical direction, so a line control library is incorporated (S126, S127).

Next, in order to generate data for controlling the output character size, a library for converting the character size into a character size code is incorporated (S128). The file existence identifier of the input data and the attribute of the input data are determined (S129), and a library for setting the input data is incorporated (S130). At this time, if the attribute of the data to be output is Japanese, a library to which a shift code is added is also incorporated (S131). Finally, a part for outputting the PID generated by the above process is created. This series of processing is performed for each field in the printout specification file to create the entire program (S132).

Although the present invention has been described with reference to the embodiments, the present invention is not limited to these embodiments and can be applied and implemented in various modes within the scope of the technical idea of the present invention. It goes without saying that they are also included in the present invention. For example, the transaction data check program automatic generation process and the check process of the present invention are not limited to the print image data forming process described in the embodiments, but can be applied to any print image data forming process. In addition, P of the present invention
The ID conversion program automatic generation process and the PID conversion process are
It can be performed regardless of whether transaction data is checked.

[0051]

As described above, according to the present invention,
Before converting the transaction data into print image data, detect the transaction data defect,
Since it can be corrected, it is possible to obtain transaction data that does not include a defective portion. Further, when a program for checking the consistency of transaction data is automatically generated, time-consuming data consistency check can be performed by other models as well, so efficient check processing can be performed.

[Brief description of drawings]

FIG. 1 is a diagram showing an example of a system configuration for implementing a print image data creating method and apparatus of the present invention.

FIG. 2 is a diagram exemplifying a record of transaction data.

FIG. 3 is a diagram illustrating a print layout.

FIG. 4 is a diagram illustrating a PID.

FIG. 5 is a flowchart of a main program showing an overall process executed by the control device 1.

FIG. 6 is a flow chart showing a designated edit processing method when an ID is not registered in the designated edit processing (S3) of FIG. 5;

7 is a flow chart showing a designated edit processing method when an ID is registered in the designated edit processing (S3) of FIG.

FIG. 8 is a diagram showing a management information input screen displayed on the display device 3;

9 is a diagram showing an input screen for transaction data MT specifications displayed on the display device 3. FIG.

10 is an input screen of the editor displayed on the display device 3. FIG.

FIG. 11 is a diagram showing an input screen for external character font new creation (S26) displayed on the display device 3;

FIG. 12 is a diagram showing an input screen for data specifications of record fields displayed on the display device 3;

13 is a diagram showing a display screen of a spacing chart displayed on the display device 3. FIG.

14 is a diagram showing a display screen of a ruled line frame displayed on the display device 3. FIG.

15 is a diagram showing a printout specification input screen displayed on the display device 3. FIG.

16 is a flowchart showing a PID formation processing method in PID formation (S8) which is a submenu of the job processing (S4) in FIG.

17 is a flowchart showing a processing method in backup / registration (S9) which is a submenu of the job processing (S4) in FIG.

FIG. 18 is an example of a record field specification file when the record layout is FIG.

FIG. 19 is an example of a fixed information file, and the menu “fixed character” in the printout specification input (S30) of FIG.
This file is generated when is selected and executed.

FIG. 20 is an example of a printout specification file when the printout specification is that of FIG.

FIG. 21 is a flowchart for explaining the contents of transaction data check processing.

FIG. 22 is a flowchart showing a process of automatically generating a transaction data check program.

FIG. 23 is a flowchart showing a PID conversion process.

FIG. 24 is a flowchart showing a PID conversion program automatic generation process.

FIG. 25 is a diagram showing a process in the case of creating a bill on output paper of a predetermined form.

FIG. 26 is a diagram showing an example of one record written in a transaction file.

FIG. 27 is a diagram showing an aspect in which transaction data should be printed on an output sheet of a predetermined form.

FIG. 28 is an example of a data format for correctly printing each piece of transaction data at a position to be printed on output paper.

[Explanation of symbols]

 1 Control Device 2 Input Device 3 Display Device 4 FD Device 5 MT Device 6 Storage Device 7 Printer 8 Network

[Procedure amendment]

[Submission date] February 18, 1994

[Procedure Amendment 1]

[Document name to be amended] Statement

[Correction target item name] 0006

[Correction method] Change

[Correction content]

In such a case, it is obvious that each data will not be printed at the correct position to be printed by simply setting the transaction data and the output paper on the printer, and each data should be printed on the output paper. In order to print correctly at the position, it is necessary to change the format of the transaction data record to the data format shown in FIG. FIG. 28 is an example of PID. FIG. 28
According to the data format shown in, the printer reads one record, first page breaks, and then takes in the next output sheet. The first line is a line feed, the second line is the first 10 digits, and the 11th digit is blank. Print the contents of the field 2 "address" in the 40th to 40th columns and start a line feed. Then, after the 3rd and 4th lines are fed back, the 5th line is blanked in the first 10 columns. Print the contents of field 1 "Name" in the 20th digit, leave the following 10 digits blank, and
The contents of field 3 "billing amount" are printed at the 1st to 35th digits and a line feed is performed. This series of data strings are arranged for the number of output cases. The Kanji IN code in FIG. 28 is a code indicating that the following data is data of 1 character and 2 bytes, and the Kanji OUT code is a code indicating the end of data of 1 character and 2 bytes.

[Procedure Amendment 2]

[Document name to be amended] Statement

[Correction target item name] 0044

[Correction method] Change

[Correction content]

After reading the record layout, discrimination processing is performed based on the data type of each field (S84).
The X item indicates the entire 1-byte character, the 9 item indicates numerical data, and the N item indicates the entire 2-byte Japanese character. Next, a check (S85) is performed, and the processing process will be described by taking the X item as an example. The transaction data for the number of digits is read from the leading position of each field that has been read previously (S86), and it is determined from the input code name whether it is within the normal range of the code table for the X item (S8).
7). At this time, the code value of the read external character is not considered as a check target. When it is determined that the input code is within the normal range of the code table, the next code value is processed and repeated for the number of digits. If the input code is determined to be outside the normal range of the code table, the error content is recorded (S88). For example, if the input transaction data is ASCII code 00 (H), it is determined that an error occurs because the character is not defined. At this time, the byte position in the transaction data where the error occurred, the code value 00 (H)
In the error file. Check processing is similarly performed for other data items.

[Procedure 3]

[Document name to be corrected] Drawing

[Correction target item name] All drawings

[Correction method] Change

[Correction content]

[Figure 1]

[Fig. 2]

[Figure 3]

FIG. 26

[Figure 4]

[Figure 5]

[Figure 6]

[Figure 8]

FIG. 19

FIG. 27

[Figure 7]

[Figure 9]

[Figure 10]

FIG. 11

[Fig. 12]

FIG. 18

FIG. 20

[Fig. 13]

FIG. 14

FIG. 15

FIG. 16

FIG. 28

FIG. 17

FIG. 22

FIG. 21

FIG. 23

FIG. 24

FIG. 25

Claims (6)

[Claims] 1. A check program automatic generation process for automatically generating a check program for checking the consistency of transaction data, which is the original data of print image data, based on the record layout, data attribute, and digit number information of the transaction data. A method for creating print image data, which is characterized by the following. 2. A print image data creating method, wherein check processing for checking the transaction data is performed by the check program generated by the check program automatic generation processing according to claim 1. 3. A method of creating print image data, characterized in that the consistency of the transaction data is checked based on the record layout, data attribute, and digit number information of the transaction data which is the original data of the print image data. 4. A storage device in which transaction data, which is original data of print image data, is stored,
An input device to which the record layout, data attribute, and the number of digits of the transaction data are input, and a check program automatic for automatically generating a check program for checking the consistency of the transaction data based on the information input to the input device. A program generation device comprising: a control device having a generation means. 5. A print image data creating device, wherein the control device has a checking means for checking the transaction data by the check program generated by the program generating device according to claim 4. 6. A storage device in which transaction data, which is original data of print image data, is stored,
The control device has an input device for inputting information on the record layout, data attributes, and the number of digits of the transaction data, and checking means for checking the consistency of the transaction data based on the information input to the input device. A print image data creation device characterized by.