Batch Processing › Setting Defaults for Batch Processing › Defining files

Defining files

CA OLQ batch retrieves records from the file you specify in the JCL. (If retrieving only from the database, you do not have to specify an input file in the JCL.) The access switch must be set to olq to read or write sequential files.

You can define the characteristics of each input file the CA OLQ batch job stream accesses by using the DEFINE FILE statement. DEFINE FILE associates a file name and file characteristics with IDD record and element entities.

Example:

If your batch job accesses an input file called INFILE, you would include the following DEFINE FILE statement in your input data stream:

DEFINE FILE INFILE RECORD EMPL-2 (3) DICT TESTDICT
 RECFM=F BLKSIZE=80 LRECL=80

• The INFILE file is used to access input data from the EMPL-2 record.
• The record definition for the EMPL-2 record is stored in the TESTDICT dictionary.
• The number in parenthesis, (3), is the version number. If no version number is specified, the default is 1.

When using DEFINE FILE, the corresponding job control language statement must name the file in the DD name:

Table 13

Defining input files:

You can also use DEFINE FILE to define the following characteristics for each input file:

• Record format (required for z/VSE)
• Block size (required for z/VSE)
• Logical record length (required for z/VSE)
• File type
• Device type
• Logical unit (z/VSE only)

Defining output files:

The output file is the file the report data is written to. You use the DEFINE FILE statement to direct the output to a file:

DEFINE FILE OUTFILE OUTPUT

This command marks the file OUTFILE as containing the report output.

The data set is written out in its unformatted condition to the output file.

If you want to use the output file as an input file, you must do so in a subsequent job step.

Defining sort work files:

During SORT requests and SELECT with GROUP BY requests, CA OLQ attempts to use the operating system sort utility. If you want CA OLQ to use the operating system sort, you must define appropriate sort work files in the batch job stream. If these sort work files are not in the job stream, CA OLQ uses its internal sort routines.

Note: CA OLQ always attempts the operating system sort. If the sort attempt fails, CA OLQ switches to the internal sort. An operating system sort utility is required for CMS users. If no operating sort utility is available, contact CA Technical Support for assistance.

For more information:

Commands and Syntax