File Management - IBM

elationship. However, the copy operation continues until enough violations
(recoverable errors) have occurred so that the ERRLVL value has been reached. If
this value is exceeded, the copy operation ends.
You can use the ERRLVL parameter to bring files with constraint relationships in
check pending status back into non-check pending status. Do this by setting up the
dependent to-file with constraints that are the same as the dependent from-file.
Then, use a CPYF command with the ERRLVL(*NOMAX) to copy all valid records.
The to-file should not contain any records. The copy command does not insert into
the to-file any records that it encounters from the from-file that would cause the
to-file constraints to go to check pending status. With ERRLVL set to *NOMAX, the
copy command processes all records in the from-file.
Other copy commands (CPYSRCF, CPYFRMTAP, CPYTOTAP, CPYFRMDKT, and
CPYTODKT) end immediately if the systems signals one of the recoverable errors
because there is no ERRLVL parameter for them.
Preventing date, time, and timestamp errors when copying
files
124 File Management V4R5
For FMTOPT(*MAP), FROMKEY with *BLDKEY, TOKEY with *BLDKEY, and
INCREL parameters, 2-digit year-date fields or values will be assumed to have:
v A century of 19 if the year is in the range from 40 to 99 OR
v A century of 20 if the year is in the range from 00 to 39
For example, 12/31/91 is considered December 31, 1991, while 12/31/38 is
considered December 31, 2038.
However, any from-files containing 2-digit year-date fields with actual internal
date values outside the range January 1, 1940 to December 31, 2039 cause input
mapping errors, and the copy operation fails.
When FMTOPT(*MAP) is used to convert or copy a from-file field date value in a
4-digit year form to a 2-digit year form, the from-file field value must be within
the range of January 1, 1940 to December 31, 2039. Otherwise, a mapping error
occurs, and the copy command sets the to-file field with its default value.
Likewise, when using a 4-digit year date as a record selection input string on
FROMKEY with *BLDKEY or TOKEY with *BLDKEY, the value must be within the
same range if the corresponding from-file field is a date field with a 2-digit
year-date. Otherwise, an error occurs. INCREL record selection is the exception to
this rule, as 4-digit year date values outside this range may be used for
corresponding 2-digit year-date fields.
See “Mapping considerations using Copy” for details about how to handle
different field types and formats.
Mapping considerations using Copy
When mapping a character field to a date, time, or timestamp field and a format
form is being used in the character field, leading zeros may be omitted from
month, day, and hour parts. Microseconds may be truncated or omitted entirely in
the character field.