File Management - IBM

The ERRLVL parameter specifies the maximum number of recoverable errors
allowed for each label pair or each member copied. The value specified for
ERRLVL indicates the total errors that are allowed on both the from-file and the
to-file that are combined for each label pair or each member copied. Each time an
error occurs, the following process runs:
1. The process increases the count for that label pair or that member by 1.
2. A message identifying the last good record that is read or written is printed on
all copy lists if TOFILE(*PRINT), PRINT(*COPIED), or PRINT(*EXCLD) was
specified.
3. The error record is printed if you specified PRINT(*ERROR).
4. Copying continues.
5. If the copy command completely copies the from-file member without
exceeding the limit, the process resets the counter to 0, and the copy of the next
member starts.
6. If the limit is exceeded during the copy of a member, copying ends and a
message is sent, even if more records or members remain to be copied.
For a database from-file, including the open query file, the recoverable errors
are:
v Those that occur when data is converted (mapped) AND
v Those caused by a damaged area on the disk (in auxiliary storage)
For a tape from-file, the recoverable errors are:
v A block length that is not valid AND
v A media-read operation from the tape volume on the device resulting in an error
For a physical to-file, the recoverable errors are:
v Those that occur when data is converted AND
v Those that occur when more than one of the same key is found
Any record that causes an error is not copied to the to-file. For a write error, the
record is printed on a PRINT(*COPIED) and PRINT(*EXCLD) printout. A message
then follows this printout. This message indicates that the record was not actually
copied. If you specified PRINT(*ERROR), the command prints the records that
caused write errors on the *ERROR listing. A message then indicates that an error
occurred. For a read error, no record is available to be printed on the copy
printouts (TOFILE(*PRINT), PRINT(*COPIED), PRINT(*EXCLD), or
PRINT(*ERROR)). However, a message prints on all specified printouts that
indicates that a record could not be read.
When the command cannot read a portion of the file from disk, partial object
damage to the contents of a database file occurs. If a file is damaged in such a way,
you can bypass the records that are in error by copying the good records and
manually adding the records that were not copied because of the damage.
Regardless of the value of the ERRLVL parameter, recoverable errors always
appear in the job log with a reply of “C” for “Cancel.”
For files that have constraint relationships, the ERRLVL parameter only affects the
to-file. If you set the ERRLVL parameter to 0, the copy command does not copy
into the file any record that causes the to-file to violate the constraint relationship.
The copy operation ends. If ERRLVL is greater than 0, the copy command does not
copy into the file any record that causes the to-file to violate the constraint
Chapter 4. Copying files 123