Control statement errors in interactive mode
Syntax errors: Incorrect control statements are rejected with appropriate error messages.
Semantic errors: An error dialog is conducted with the user.
Control statement errors in batch mode
Syntax or/and semantic errors: As soon as an incorrect statement is detected, all statements up to the next STEP or END statement are skipped.
DMS error messages, error code
DMS error messages are output for the user (missing passwords, ACCESS=*READ, crypto password, etc.). The DMS error code reported is output with additional PAMCONV-specific information in certain cases.
Errors during conversion
If errors occur during processing of a CONVERT-FILE statement before the target file has been successfully generated and closed, the incomplete target file (or the intermediate file) is deleted and the source file is retained regardless of the explicitly or implicitly (default value) specified FILE-DISPOSAL operand of the MODIFY-CONVERT-FILE-DEFAULTS statement. Successful closure of the target file is acknowledged with a corresponding message. The following error situations are possible after successful closure of the target file (or intermediate file):
The source file cannot be closed properly. Conversion has been successfully concluded, but the activities specified explicitly or implicitly (default value) in the FILE-DISPOSAL operand are not performed.
Both the source and the target file have been successfully closed, and in accordance with the conversion specification of the FILE-DISPOSAL operand the source file is to be replaced with the target file (REPLACE or RENAME), but the source file cannot be deleted. The same procedure as above applies.
The source file is to be replaced with the target file; the source file has been deleted, but the renaming operation in accordance with the conversion value REPLACE in the FILE-DISPOSAL operand cannot be performed. In this case the end result is the same as if RENAME had been specified in the FILE-DISPOSAL operand.
Subsequently the next statement is executed.
Inconsistent files
If the source file is an ISAM/SAM file or a load module, it is subjected to a strict check for formal consistency during conversion. Inconsistencies may be subdivided into two groups:
The inconsistency is such that loss of data is to be expected during further conversion (e.g. in the case of defective index entries). Conversion is aborted with an appropriate message.
There is a formal inconsistency, but loss of data can be excluded (e.g. reserved fields or free blocks do not contain binary zero). In this case a warning is output and conversion continues.
Subsequently the next statement is executed.
Incompatible files
Operation of NK formats is not fully compatible. Consequently, various incompatibilities result from conversion into NK format. See the section on PAM key elimination in the “Introductory Guide to DMS” [4 (Related publications)].
As soon as incompatibilities are sensed which prevent proper conversion, the conversion process is aborted with an appropriate message (hard incompatibility).
If incompatibilities are detected which reduce performance but do not essentially prevent conversion, a warning is issued and conversion continues (soft incompatibility).
Subsequently the next statement is executed.