Record format field mapping - assure_mimix - 10.0

Assure MIMIX Promoter User Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Promoter User Guide
Copyright
2021
First publish date
1999
Last updated
2023-08-01
Published on
2023-08-01T14:40:24.932940

The Record format field mapping (FMTOPT) parameter controls how records within a file are copied. The value *NONE indicates that no field mapping or dropping occurs during the copy operation. The value *NONE is only valid when the from-file and to-file have the same record format. Record formats are the same only if every field exists in each file and are identical in both files. When *NONE is valid, null values are copied.

If the value *NOCHK is specified, null values are ignored and no conversion of date/time/timestamp data occurs. If the record formats of the database files are different, the copy operation continues despite the differences. Record data is copied directly (left to right) from one file to the other.

When *MAP is specified, fields with the same name in the from-file and to-file record formats are copied. Any fields in the to-file that do not exist in the from-file format are set as follows:
  • To the default value specified on the DFT keyword for the data description specification (DDS) of the to-file

  • To zero for numeric fields

  • To blanks for character fields,

  • To the current date/time/timestamp for date/time/timestamp fields

  • To null value for null-capable fields.

If any of the field names in the from-file record format do not exist in the to-file format, you should specify *DROP for field-level mapping. If *DROP is specified, you can also specify *MAP. When *DROP is specified, all the field names that exist in both record formats must have the same attributes and relative positions in the from-file and to-file record formats, otherwise *MAP must also be specified. Null values are copied.