Table of Contents

Search

  1. Preface
  2. PowerExchange Navigator Introduction
  3. Data Maps
  4. Data Maps for Specific Data Sources
  5. Copybooks
  6. Registration Groups and Capture Registrations
  7. Extraction Groups and Extraction Maps
  8. Personal Metadata
  9. Database Row Test
  10. PowerExchange Navigator Examples
  11. Appendix A: PowerExchange Functions for User-Defined Fields
  12. Appendix B: User Access Method Programs
  13. Appendix C: Application Groups and Applications
  14. Appendix D: Data Map Properties
  15. Appendix E: Record, Field, and Table Properties
  16. Appendix F: DTL__CAPXTIMESTAMP Time Stamps
  17. Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook

Navigator User Guide

Navigator User Guide

Data Map Properties - SEQ Access Method

Data Map Properties - SEQ Access Method

View or edit properties for a data map defined for flat file or sequential data set.
Filename
The full path and file name of the sequential data set or flat file. If the file is located on the local system, click the Browse button to browse to the file. Valid characters are ASCII characters and the pound and yen sign.
  • Do not enclose the name in single quotation marks. PowerExchange uses the specified name as the fully qualified file name and prevents z/OS from adding a a user ID as a prefix.
  • If you are importing a Db2 file from IBM i, the file you import must be a single-record format file.
Fixed
For a fixed-length binary data file, select this option.
In the
Size
box, enter the record length.
A fixed-length binary file is exactly divisible by the specified record length.
Variable
For a variable-length data file, select this option.
In the
Variable
list, select one of the following variable-length data file types:
  • VBI2
    . Data length is 2-byte value, where length "I"ncludes 2-byte length.
  • VBI4
    . Data length is 4-byte value, where length "I"ncludes 4-byte length.
  • VBX2
    . Data length is 2-byte value, where length e"X"cludes 2-byte length.
  • VBX4
    . Data length is 4-byte value, where length e"X"cludes 4-byte length.
  • VS
    . Variable-length stream data file. In the data file, no record boundaries exist. The records are field delimited and are not of fixed length.
    You can use this option for data that you transferred between a UNIX or Windows system and an i5/OS or z/OS system.
    For files that you transferred from UNIX or Windows to z/OS, verify that the LRECL value that you define for the data set is greater than the length of the longest record in the UNIX or Windows file. For files that you transferred from UNIX or Windows to i5/OS, verify that the record length that you specified on the Create Physical File (CRTPF) command is greater than the length of the longest record in the UNIX or Windows file.
    If you select this option, the
    Skip First
    n
    Records from File
    data map property is not available. Also, you cannot use the
    Skip First
    n
    Rows
    option in the
    Database Row Test
    dialog box to skip a specific number of initial rows when performing a database row test.
  • VBP2
    . VLI length value includes 4-byte prefix, 2-byte VLI, and two bytes of NULLS. Equates to z/OS variable unblocked.
  • VBM2
    . VLI length value is "M"inus, includes 4-byte prefix, 2-byte VLI, two bytes of NULLS.
  • VBB2
    . VLI length value includes 4-byte prefix and 4-byte Block Descriptor Word. Equates to z/OS Variable Blocked. Use for files that are transferred to an ASCII system to retain the Block and Record Descriptor Words.
On Linux, Windows, and UNIX, you can process or create variable-length binary data by using these file types. With all these file types except VS, the data is preceded by one of the following integer-length fields:
  • 16-bit short integer, which is two bytes
  • 32-bit integer, which is four bytes
The length contained in this field provides the length of the actual data and might include the length of the prefix.
Default
If you want PowerExchange to assign the file type based on the operating system and file attributes, select this option. Use this option if you are reading mainframe data that did not originate in another system.
Default
is selected by default.
Encoding
The encoding scheme. The options are:
  • Default
    . PowerExchange uses the default encoding scheme for the operating system.
  • EBCDIC
    . EBCDIC.
  • ASCII HIEND
    . ASCII high endian.
  • ASCII LOEND
    . ASCII little endian.
    The encoding scheme applies to both the record descriptors and the data in the record.
Default is
Default
.
Codepage
The code page that describes the character set for the character data in the database. For the
Default
code page, PowerExchange uses the default code page for the operating system.
Multibyte code pages are available for sequential data sets or flat files.
Default is
Default
.
Field Separator
If the data file is a character-separated file, select this option to enter the character that is used to separate fields in the data file.
Valid characters are ASCII characters and the pound and yen sign.
If the field separator character is a hexadecimal combination, enter it in the following format:
x'
nn
'
Merge Adjacent Separators
Merges adjacent separators into a single separator.
Enabled if the
Field Separator
option is selected.
Field Delimiter
Enter the character that is used to delimit data within a field. For example, the quote (“) character might be used to enclose strings within a field.
Enabled if the
Field Separator
option is selected.
Valid characters are ASCII characters and the pound and yen sign.
Skip First
n
Records from File
If the file has one or more header records that are not needed for PowerExchange operations, enter the number of header records to skip.
Valid values are 0 to 2147483647.
Default is 0, which causes no rows to be skipped.
File List Processing
Uses file list processing for the data map.
View File
Displays the data file.
Enabled after you enter a file name.
For more information about defining data map properties of sequential files for bulk data movement, see the chapter, "Sequential File Bulk Data Movement," in the
PowerExchange Bulk Data Movement Guide
.

0 COMMENTS

We’d like to hear from you!