COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

23
Cannot determine file name ( error )
program_name.logical_name
Cause
The CRE could not determine the physical file name associated with
program_name.logical_name.
Effect
The run unit terminates abnormally.
Recovery
Correct the program_name.logical_name and rerun your program. For information on
ASSIGN commands, see ASSIGN Command (page 582) and the TACL Reference Manual.
24
Conflict in application of ASSIGN
program_name.logical_name
Cause
ASSIGN values in your TACL environment conflict with each other. For example:
ASSIGN A, $B1.C.D
ASSIGN *.A, $B2.C.D
The first ASSIGN specifies that the logical name A can appear in no more than one loadfile.
The second assign specifies that the name A can appear in an arbitrary number of loadfiles.
The CRE cannot determine whether to use the file C.D on volume $B1 or on volume $B2.
Effect
The run unit terminates abnormally.
Recovery
Correct the ASSIGNs in your TACL environment. For information on ASSIGN commands, see
ASSIGN Command (page 582) and the TACL Reference Manual.
25
Ambiguity in application of ASSIGN
logical_name
Cause
An unqualified file name (one without the program-name or the asterisk (*) prefix) specified by
an active ASSIGN command corresponds to more than one COBOL file in the run unit.
Effect
The run unit terminates abnormally.
Recovery
Either qualify the file name or change the program to prevent duplicated names.
26
Invalid PARAM value text ( error )
PARAM name 'value')
Cause
A PARAM specifies a value that is not defined by the CRE. For example, the value for a DEBUG
PARAM must be either ON or OFF. The CRE reports this error if a DEBUG PARAM has a value
other than ON or OFF. error, if present, is a Guardian file system error.
1186 Run-Time Diagnostic Messages