First of all, choose an input file:
- The input file name for the defined operation.
Then, use parameters to describe the input file:
- The file format for the input file. Valid values are:
- Micro Focus
The default format is Micro Focus and this would normally be used for files downloaded from the host and recreated on the
PC. If the chosen file is an emulation of the mainframe VSAM entry-sequenced data set, choose ESDS or Extended-ESDS to provide
the emulation of VSAM ESDS on the PC.
- The file organization for the input file. Valid values are:
- Line sequential
- Indexed sequential
- ANSI Mainframe Report (The mainframe report with ANSI carriage control characters)
- Machine Mainframe Report (The mainframe report with machine code carriage control characters)
- PC Print.
- The record format for the input file. Valid values are:
Variable length Mainframe Report files are not supported.
- The character encoding used in the input file. Valid values are:
Note: The Windows environment uses the EBCDIC and ANSI character encodings, and the UNIX/LINUX environments use the EBCDIC and ASCII
character encodings. The character encodings used in the ANSI and ASCII code pages are different.
- The type of floating-point format that is used in the input file.
- An indication that data compression is used for the input file. Valid values are:
This should only be set to On if the file was created with data compression.
- The minimum record length for the input file.
If the file is fixed length this should be set to the same value as the maximum record length.
- The maximum record length for the input file.
If the file being created is indexed, the keys are defined using the following records.
- The start position of the key is either the column number or offset depending on the version of the profile being used. A
colon is used to separate the position and length fields.
- DFS Profile Files use a start position (column) starting at 1 with the prime key being in the format
position:length (for example, 1:12).
- DataTools Profiles use an offset starting at 0 with the prime key being in the format
offset:length (for example, 1:12).
A second record in the profile file sets the key flags required for the indexed file being created. The flags are separated
by a comma (for example: d,cd).
||allow duplicate record keys
||sparse character - not supported
||compress duplicate record keys
||compress leading spaces on record keys
||compress trailing spaces on record keys