JP2016081126A - Job control language automatic generation program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To flexibly adjust a generated job control language (JCL) while reducing the workload of generating the JCL.SOLUTION: A JCL automatic generation program 120 reads, as an input, a job flow chart in a job flow file 131 and a template of a JCL in a rule file 132, and generates, as an output, a job control file 133 including the JCL. At this time, a template described for each job flow component showing a process on the job flow is applied to the job flow chart.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a technique for automatically generating a job control language used by a general-purpose machine.

  The job control language (JCL) is a script language for job control that specifies, for a computer, the contents of a job and the name of a device to be used in a general purpose machine (mainframe). The job control language can be described manually or can be created using dedicated editing software.

  The following Patent Document 1 describes a technique for creating a job flow and JCL. In this document, a job flow component is connected on the screen and a job attribute or the like is input to generate JCL according to the input.

Japanese Patent Application Laid-Open No. 09-044346

  In the technique described in Patent Literature 1, JCL is created according to the job flow diagram created on the screen (for example, FIG. 12 of the literature). However, although the JCL generated at this time is thought to reflect the contents of the job flow diagram, it seems that each specific control statement is created in a fixed manner according to some rules. .

  Therefore, in this document, when individual control statements of the generated JCL do not match, for example, parameters in the real environment, it is considered that the generated JCL must be corrected manually by the developer. Specifically, when the model of the general-purpose machine is changed, it is necessary to change various parameters on the JCL along with this, but the technique described in the cited document 1 flexibly copes with such a change. It is difficult.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a technique capable of flexibly adjusting the generated JCL while reducing the work load of generating the JCL.

  The job control language automatic generation program according to the present invention automatically generates JCL by reading a rule file in which a JCL template is described for each job flow component and applying the template to a job flow diagram.

  According to the job control language automatic generation program according to the present invention, the automatically generated JCL can be flexibly customized.

1 is a configuration diagram of a computer 100 that executes a job control language automatic generation program 120 according to Embodiment 1. FIG. It is an example of a job flow diagram (first half) described in a job flow file 131. It is an example of a job flow diagram (second half) described by a job flow file 131. FIG. 3 is a diagram showing a start part of a job control language describing the job flow described in FIGS. 2A to 2B. It is a figure which shows the job control language which described the job flow demonstrated in FIG. 2A. It is a figure which shows the job control language which described the job flow demonstrated in FIG. 2B. It is a figure which shows the start part of the rule file. It is a figure which shows the location which described the template corresponded to JCL demonstrated by STEP0010 of FIG. 3B among the rule files. FIG. 4 is a diagram showing a part in which a template corresponding to JCL described in STEP 0020 of FIG. 3B to STEP 0040 of FIG. It is a figure which shows the location which described the template equivalent to the completion declaration part of FIG. 3C among the rule files.

<Embodiment 1>
FIG. 1 is a configuration diagram of a computer 100 that executes a job control language (JCL) automatic generation program 120 according to the first embodiment of the present invention. The computer 100 is a computer that executes processing for automatically generating JCL, and includes a CPU (Central Processing Unit) 110, a JCL automatic generation program 120, and a storage unit 130.

  The CPU 110 is a processor that executes a program. In the following, for convenience of description, the program may be described as an operation subject, but it is the CPU 110 that actually executes the program.

  The JCL automatic generation program 120 reads the job flow file 131 and the rule file 132 as inputs and generates a job control file 133 as an output. Specific operations of the JCL automatic generation program 120 will be described later.

  The storage unit 130 is a storage device such as a hard disk device. The JCL automatic generation program 120 can be stored in the storage unit 130 or can be stored in another appropriate storage device.

  The storage unit 130 stores a job flow file 131, a rule file 132, and a job control file 133. Specific examples of these files will be described later.

  FIG. 2A is an example of a job flow diagram (first half) described by the job flow file 131. The job flow file 131 is a drawing data file created by appropriate drawing creation software, and describes a job flow diagram as illustrated in FIG. 2A. A job flow diagram can be described by connecting job flow components with arrows. In each job flow component, an attribute value to be described later is described.

  A job flow can be formed by combining steps composed of a process, inputs to the process, and outputs from the process. For convenience of explanation, the job flow shown in FIG. 2A is divided into two steps STEP0010 and STEP0020. Each step has the above-described configuration.

  In STEP0010, a process SORT 53 is a process for sorting input data, and two data sets AA001 (0) and SORT. AA001 is received as an input, and one data set && AA001 is output as a processing result.

  An attribute of the data set can be described in the job flow component representing each data set.

  Data set AA001 (0) has a record length of 500 BYTE, the maximum number of records is 200000, and the DD name is SORTIN. The numbers in parentheses () are generation numbers, which indicate that the data set is generation-managed (that is, a new generation number is assigned when data is updated). Data set SORT. AA001 is a SYSIN data set.

  Data set && AA001 has the DD name SORTOUT, and the record length and the maximum number of records are the same as data set AA001 (0). An asterisk * indicates that the data set is delivered as input for another process. The HEB 5401I next to * is a DD name used when the next process receives the data set && AA001 as an input.

  In STEP0020, the process MEBPC 30 is a batch process (a general program other than SORT), and receives the data set BB001 as an input together with the output of the process SORT 53. Data set BB001 is not an output from the process but an existing data file stored on the storage device. The DD name of the data set BB001 is * HEB5401I. The process MEBPC 30 outputs two data sets && BB0011 and && BB0012 as outputs. The attributes of each data set are as described in FIG. 2A.

  The connectors 1 and 2 arranged at the end of FIG. 2A indicate that the subsequent job flow continues to the connector having the same number.

  FIG. 2B is an example of a job flow diagram (second half) described by the job flow file 131. FIG. 2B shows a continuation of the job flow shown in FIG. 2A. As in FIG. 2A, the process and its input / output are set as a set and divided into two steps, STEP0030 and STEP0040.

  The process MEBPC 35 in STEP0030 receives the data set && BB0011 from the connector 1 as an input. The process MEBPC 40 in STEP0040 receives the data set && BB0013 output from the process MEBPC 35 and the data set && BB0012 following the connector 2 as inputs, and outputs two data sets AA001 (+1) and BB003.

  +1 described in parentheses () of data set AA001 (+1) indicates that the generation number of data set AA001 is incremented by one. A job flow component similar to the OR symbol represents a hard disk, and a job flow component with a drawer attached to the lower right of the circle represents a tape device.

  FIG. 3A is a diagram showing a start portion of a job control language describing the job flow described in FIGS. 2A to 2B. Hereinafter, each part of FIG. 3A will be described.

  JCL needs to describe the start declaration at the beginning. In the start declaration, it is necessary to describe the job name (JEBMP99), class name (C), and user name (USER00). These will be described again in the description of the rule file 132 described later.

  In a general-purpose machine, if the data file output from the process already exists on the storage device, the process ends in error (however, depending on the specifications of the general-purpose machine). Therefore, it is necessary to delete the data set that the job flow finally outputs before starting the job flow. This process is called advance deletion. In the job flow described with reference to FIG. 2B, since the data set AA001 () is a generation management file, it is not necessary to delete in advance, but the data set BB003 needs to be deleted in advance. Therefore, the data set BB003 is deleted by the DELETE statement.

  FIG. 3B is a diagram showing a job control language describing the job flow described in FIG. 2A. STEP0010 executes the process SORT 53, inputs the data set AA001 (0), and outputs the data set && AA001. The SYSIN data set (SORT.AA001) is a data set that specifies parameters for sorting (eg, a field to be sorted), and is therefore defined separately.

  The parameter DISP (DISPosition) = SHR is specified at the location (DD name: SORTIN and DD name: SYSIN) where the input data set is defined. This specifies that a shared data file (that is, a data file that may be accessed simultaneously by another process) is shared.

  The parameter DISP = (NEW, PASS) is specified at the location (DD name: SORTOUT) where the output data set is defined. This designates that a new data file is created and the data file is transferred to another process. The UNIT parameter specifies the type of storage device (hard disk: SYSDA or tape device: VTS). The SPACE parameter specifies the storage capacity to be secured on the storage device, and can be calculated from one track size and the maximum size of the data set. The RLSE designation designates that an extra storage area is released when the number of records is less than the maximum number.

  STEP0020 specifies that the process FHDBAT1 is executed and the process MEBPC30 is executed in the process FHDBAT1. Since the database may be accessed in batch processing, the database access processing is defined in advance in a common process, and a process on the job flow is called in that. The beginning part of STEP0020 describes that. The same applies to STEP0030 and STEP0040 described later.

  The first input of the process MEBPC 30 is Data Set && AA001, and its DD name is HEB5401I. Since the data set && AA001 is a data file temporarily created to exchange data between processes, the DISP parameter specifies an OLD indicating an existing file and indicates that the data set is deleted when the delivery is completed. DELETE to be specified is specified.

  The second input of the process MEBPC 30 is a data set BB001, which is an existing data file and may be accessed simultaneously by other processes. Therefore, SHR indicating shared access is designated as a DISP parameter.

  The two outputs of the process MEBPC 30 are specified as described with reference to FIG. 2A according to the same description rule as the output of STEP0010. The record length of each data set is also specified as shown in FIG. 2A.

  FIG. 3C is a diagram showing a job control language describing the job flow described in FIG. 2B. Each step will be described below.

  In STEP0030, the process MEBPC 35 is executed in the process FHDBAT1. The input is && BB0011, which continues from connector 1. Since the data file is temporarily created to exchange data between processes, OLD and DELETE are designated as DISP parameters as in the case of input to the MEBPC 30. The output is && BB0013, and the DISP parameter, the SPACE parameter, and the UNIT parameter are specified in the same manner as in the process MEBPC30. The record length is also specified as shown in FIG. 2B.

  In STEP0040, the process MEBPC 40 is executed in the process FHDBAT1. The inputs are && BB0012 and && BB0013 output from the process MEBPC0035 following the connector 2. Since the data file is temporarily created to exchange data between processes, OLD and DELETE are designated as DISP parameters as in the case of input to the MEBPC 30.

  The first output of the process MEBPC 40 is AA001 (+1). Since this data set is stored in the storage device as the final output, CATLG is specified as the DISP parameter. The UNIT parameter, SPACE parameter, and record length are the same as in the preceding processes.

  The second output of the process MEBPC 40 is BB003. Similarly, CATLG is specified as the DISP parameter. Since BB003 is written to the tape device, VTS is specified as the UNIT parameter. The record length is the same as each preceding process. For tape devices, the SPACE parameter is omitted because it is unnecessary.

  When each STEP ends, an end declaration is described at the end of the JCL. This end declaration is fixed.

<Embodiment 1: About Rule File 132>
The JCL automatic generation program 120 automatically generates the JCL described in FIGS. 3A to 3C according to the job flow diagrams described in FIGS. 2A to 2B. At this time, the JCL automatic generation program 120 uses the JCL template described in the rule file 132. This JCL template is defined in consideration of the following points from the viewpoint of reducing the number of parameters that a developer should describe in the job flow file 131 as much as possible and enhancing the versatility of the template.

(Feature 1 of the rule file 132)
When multiple input / output data sets of the same type are used, the template that defines the part is defined so that it can be reused repeatedly. For example, when a plurality of data sets are input for a certain process, there is only one template that defines the input, and the JCL automatic generation program 120 repeatedly uses the single template. The same applies to the output data set. Thereby, the versatility of the template can be improved and the description of the rule file 132 can be simplified. Details will be described again later in the description of sub-blocks in FIG. 4A.

(Feature 2 of the rule file 132)
The rule file 132 describes a template for instructing the advance deletion described in FIG. 3A. Since pre-deletion is a fixed process, it is suitable to be defined by a template. Details will be described later in FIG. 4A.

(Feature 3 of the rule file 132)
Since data set names, process names, DD names, etc. in the job flow are variable, it is desirable to describe them in the job flow diagram. Therefore, these names are defined as variable parameters on the template.

(Feature 4 of the rule file 132)
Data sets exchanged between processes are created temporarily, and should be deleted after the exchange is completed. On the other hand, a data set created on the storage device separately from the job flow is likely to be accessed by other job flows or processes, and should be shared. On the other hand, a data set output by a process is always created anew, and whether it is handed over to the next process or the final output depends on the job flow. Since these data characteristics are determined according to the input / output relationship between the data set defined by the job flow and the process, they can be derived from the job flow diagram. Therefore, the DISP parameters for specifying these data access characteristics are defined as parameters acquired from the job flow diagram.

(Feature 5 of the rule file 132)
When a process writes a data set to the hard disk, it is necessary to specify the storage capacity to be secured. The storage capacity to be secured can be calculated from the record length, the maximum number of records, and the size of the storage device per track. Since the former two are closely related to the application specifications, they are defined as parameters to be described in the job flow diagram. Since one track size is a relatively fixed parameter, it is defined in the template.

  FIG. 4A is a diagram illustrating a start portion of the rule file 132. [] Indicates the section name of the template. A character string surrounded by% at both ends is a variable parameter. The CNT parameter indicates the number of template lines described in the section.

  In the start section of the rule file 132 (portion starting from [START]), a template corresponding to the JCL start declaration described in FIG. 3A is described. Since the job name (% JOB%), job class name (% CLASS%), and user name (% USER%) are parameters specific to the job flow, they are defined as variable parameters. These parameters may be described in an appropriate place in the job flow file 131, or may be input by displaying an input dialog on the screen by the JCL automatic generation program 120 or an internal script of the job flow file 131.

  In the next section of the start declaration (the part starting with [ERACE]), a JCL template for instructing prior deletion is described. Since the number of data sets to be deleted in advance depends on the job flow, it is desirable to define the template of the part so that it can be repeated. Therefore, in FIG. 4A, this portion is cut out as a sub-block [ERACE_DD].

  The JCL automatic generation program 120 identifies the data set excluding the generation management data set from the job flow diagram described in the job flow file 131, and the data set name is the last line in FIG. 4A. With the variable parameter% DSN%. When there are a plurality of data sets to be deleted in advance, [ERACE_DD] sub-blocks are repeatedly applied for the number of data sets.

  The JCL automatic generation program 120 can replace the template shown in FIG. 4A with the JCL described in FIG. 3A by the above processing.

  FIG. 4B is a diagram illustrating a part in which a template corresponding to the JCL described in STEP0010 in FIG. 3B is described in the rule file 132. Since the SORT process and the batch process differ in the way of describing JCL, each template is defined individually. The batch process template will be described later with reference to FIG. 4C.

  The% STEP% parameter is a variable parameter that is replaced by a step number. The JCL automatic generation program 120 automatically assigns step numbers by counting the number of steps composed of combinations of processes / input data sets / output data sets described in FIGS. 2A to 2B.

  The% PROC% parameter is a variable parameter that is replaced by the process name of the SORT process. The JCL automatic generation program 120 acquires the process name of the SORT process from the job flow diagram, and replaces the% PROC% parameter with this.

  The [SORT_IDD] sub-block is a template of a part that defines an input to the SORT process. However, the SYSIN data set is excluded. Since the number of input data sets depends on the job flow, it is defined as a sub-block so that it can be repeated. The JCL automatic generation program 120 acquires the input data set name from the job flow diagram, and replaces the% DSN% parameter in the [SORT_IDD] sub-block with this. The DISP parameter specifies the SHR that specifies the shared access in a fixed manner, but when sorting the data delivered from another process, it can be a variable parameter as in the [BATCH_IDD] sub-block described later.

  The [SORT_ODD] sub-block is a template of a part that defines an output from the SORT process. Since the number of output data sets depends on the job flow, it is defined as a sub-block so that it can be repeated. The JCL automatic generation program 120 acquires the output data set name from the job flow diagram, and replaces the% DSN% parameter in the [SORT_ODD] sub-block with this.

  When the output data set is the final output of the job flow, the JCL automatic generation program 120 specifies CATLG described in FIG. 3C as the DISP parameter. When the output data set is transferred to the next process, the JCL automatic generation program 120 specifies NEW / PASS described in FIG. 3B as the DISP parameter. The output destination of the output data set can be acquired from the job flow diagram.

  The JCL automatic generation program 120 acquires the device type (that is, the type of job flow component representing the device) to which the output data set is written from the job flow diagram, and replaces the% UNIT% parameter with the device type.

  The JCL automatic generation program 120 acquires the data size per track described later from the rule file 132, and further acquires the record length and the maximum number of records of the output data set from the job flow diagram. The number of tracks to be secured for writing the output data set can be obtained by (total number of records) / (1 track size / record length). The JCL automatic generation program 120 replaces the% DISKSPACE% parameter with the obtained value.

  The JCL automatic generation program 120 acquires the SYSIN data set name input to the SORT process on the job flow diagram, and replaces this with the% DSN% parameter of the DD name SYSIN part.

  The JCL automatic generation program 120 can replace the template shown in FIG. 4B with the JCL described in STEP0010 of FIG. 3B by the above processing.

  FIG. 4C is a diagram illustrating a part in which a template corresponding to the JCL described in STEP 0020 in FIG. 3B to STEP 0040 in FIG. 3C is written in the rule file 132. Since these steps are all batch processes, JCL can be automatically generated using the same template.

  The% STEP% parameter is the same as in FIG. 4B. The% SYSTEM% parameter and the% PLAN% parameter may be entered in an appropriate place in the job flow file 131, or an input dialog is displayed on the screen by the JCL automatic generation program 120 or the internal script of the job flow file 131. You may let them.

  The [BATCH_IDD] sub-block is a part template that defines the input to the process. Similar to [SORT_IDD], it is defined as a repeatable sub-block. The JCL automatic generation program 120 acquires the input data set name and its DD name from the job flow diagram, and replaces the% DSN% parameter and the% DDN% parameter in the [BATCH_IDD] subblock with these. When the input data set is an output from another process, the JCL automatic generation program 120 specifies OLD / DELETE described in FIG. 3B as the DISP parameter. When the input data set is existing data on the storage device, the JCL automatic generation program 120 specifies SHR as the DISP parameter.

  The [BATCH_ODD] sub-block is a template of a part that defines the output from the process. Similar to [SORT_ODD], it is defined as a repeatable sub-block. The JCL automatic generation program 120 acquires the output data set name and its DD name from the job flow diagram, and replaces the% DSN% parameter and% DDN% parameter in the [BATCH_ODD] subblock with these. % DISP%,% UNIT%, and% DISKSPACE% are the same as those in the [SORT_ODD] sub-block. The% RECLENGTH% parameter is replaced with the record length specified on the job flow diagram.

  The JCL automatic generation program 120 can replace the template shown in FIG. 4C with the JCL described in STEP0020 in FIG. 3B to STEP0040 in FIG.

  FIG. 4D is a diagram illustrating a part in which a template corresponding to the end declaration part of FIG. 3C is described in the rule file 132. The [END] section describes the end declaration template. Since the end declaration is fixed, there are no variable parameters.

  The [DISKSPACE] section describes basic data for calculating the storage capacity of the hard disk to be secured. The BASE_SIZE parameter specifies the data size per track. The JCL automatic generation program 120 uses this numerical value to calculate the% DISKSPACE% parameter described above. Since this section is not a template itself, it is not described in JCL.

  The JCL automatic generation program 120 receives the job flow diagram described in the job flow file 131 as an input, and the job flow described in FIG. Apply to As a result, the job control file 133 as described with reference to FIGS. 3A to 3C can be automatically generated.

<Embodiment 1: Summary>
The JCL automatic generation program 120 according to the first embodiment reads a JCL template to be generated based on the job flow diagram from the rule file 132, and reflects the job flow, the data set name, and the like. Thereby, JCL to be automatically generated can be flexibly customized according to individual specific specifications such as a general-purpose machine and its OS.

  The JCL automatic generation program 120 according to the first embodiment identifies a data set that is not generation-managed among the data sets output at the end of the job flow, and automatically generates a JCL statement that deletes the data set in advance. As a result, it is possible to reduce the trouble of manually creating a JCL sentence related to prior deletion. Moreover, even when there are a plurality of data sets to be deleted in advance, all of them can be automatically dealt with by a single [ERACE_DD] sub-block.

  The JCL automatic generation program 120 according to the first embodiment inputs data depending on whether a data set input to a process is an output of another process or created separately from the job flow. The DISP parameter of the definition part is automatically set. As a result, it is possible to reduce the trouble of creating a JCL statement that defines the input to the process.

  The JCL automatic generation program 120 according to the first embodiment sets the DISP parameter in the output definition portion according to whether the data set output by the process is delivered to another process or the final output of the job flow. Set automatically. Thereby, it is possible to reduce the trouble of creating a JCL statement that defines the output from the process.

  The JCL automatic generation program 120 according to the present embodiment 1 determines the storage capacity of a hard disk to be secured for writing a data set output by a process, one track size defined by the rule file 132, and each job flow diagram. Automatic calculation based on parameters. As a result, it is possible to further reduce the trouble of creating a JCL statement that defines the output from the process.

<Embodiment 2>
The job flow file 131 described in the first embodiment can be created in an arbitrary format as long as the JCL automatic generation program 120 can read parameters such as the job flow, each job flow component, and each name. For example, it can be created by a graphic editing function such as spreadsheet software, document creation software, presentation software, etc. that are generally available in the market. When the data format of the job flow file 131 is changed, if the JCL automatic generation program 120 modifies only the process of reading the job flow file 131, the same function as before the change can be used.

  100: computer, 110: CPU, 120: JCL automatic generation program, 130: storage unit, 131: job flow file, 132: rule file, 133: job control file.

Claims (9)

A program for causing a computer to execute processing for generating a job control file described in a job control language used by a general-purpose machine,
A job flow acquisition step of reading a job flow file describing a job flow diagram defining a job flow to be executed by the general-purpose machine;
A rule acquisition step of reading a rule file describing rules for generating the job control file according to the job flow diagram;
Generating the job control file by applying the rule file to the job flow defined by the job flow diagram;
And execute
The rule file describes the job control language template describing the job flow defined by the job flow diagram for each type of job flow component representing a process on the job flow,
In the generation step, the job control language is generated by causing the computer to replace the job flow component with the template. The job flow diagram defines the job flow in which one or more data is input to a process on the job flow, or the process outputs one or more data,
The rule file describes an input definition template or an output definition template as a template of the job control language that defines input to the process or output from the process.
In the generating step, the computer
The input definition template is repeatedly used as many times as the number of data input to the process in the job flow, or the output definition template is repeatedly used as many times as the number of data output from the process. The job control language defining the input to the process or the output from the process is generated by using the single input definition template or the single output definition template. The job control language automatic generation program described. The job flow diagram defines that one or more output data files are output as the output of the job flow,
The rule file is a template for the job control language that specifies that the output data file is to be deleted before starting the job flow if the output data file exists at the time before starting the job flow. Has written,
In the generating step, the computer
After specifying the output data file on the job flow diagram, in accordance with the description of the rule file, the job control language for deleting the specified output data file is the same as the job control language for describing the job flow. The job control language automatic generation program according to claim 1, wherein the job control language automatic generation program is generated before. In the generating step, the computer
The output data file except for the output data file whose generation is managed on the general-purpose machine is specified, and the job control language for deleting the specified output data file is generated. The job control language automatic generation program according to claim 3. The job flow diagram describes the data set name of the data file along with the connection relationship between the process and the data file on the job flow,
In the generating step, the computer
Obtaining from the job flow file a data set name of the data file input to or output from the process on the job flow;
Generating the job control language specifying a data set name obtained from the job flow file as an input to or output from the process;
The job control language automatic generation program according to any one of claims 1 to 4, wherein the program is executed. In the generating step, the computer
If the input to the process is a data file delivered from another process, specify the existing data file as the type of input to the process and specify to delete the existing data file that has been input to the process Generating the job control language;
If the input to the process is a shared data file that can be accessed simultaneously by other processes, generating the job control language, specifying the shared data file as a type of input to the process;
The job control language automatic generation program according to claim 5, wherein: In the generating step, the computer
If the output from the process is a data file delivered to another process, specify a new data file as the type of output from the process and specify that the data file is delivered to another process Generating the job control language;
When the output from the process is a data file output as the final output of the job flow, a new data file is designated as the output type from the process and the data file is output as the final output of the job flow Generating the job control language, designating that
7. The job control language automatic generation program according to claim 5, wherein: The rule file is
A storage capacity per writing unit of a storage device into which the process writes a data file;
A template for the job control language that specifies to reserve a storage area on the storage device when writing a data file to the storage device;
Is described,
The job flow diagram describes the record length and the maximum number of records of a data file written to the storage device,
In the generating step, the computer
A storage area to be secured on the storage device using the record length and the maximum number of records described in the job flow diagram, and the storage capacity per writing unit described in the rule file Calculating the size of the
Generating the job control language for securing a storage area of the calculated size on the storage device;
8. The job control language automatic generation program according to claim 1, wherein the program is executed. The job control language automatic generation program according to any one of claims 1 to 8, wherein the job flow file is a file having a data format created by a drawing creation application executed on the computer.

Images