C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

Cause
The CRE could not obtain the name of the program file from the operating system.
Effect
The CRE terminates the program.
Recovery
Consult your system administrator.
23
Cannot determine filename ( error ) program_name.logical_name
Cause
The CRE could not determine the physical file name associated with
program_name.logical_name.
Effect
The CRE terminates the program.
Recovery
Correct the program_name.logical_name and rerun your program. For general information
on ASSIGN commands, see the TACL Reference Manual. For more details on using ASSIGNs,
see the reference manual for your program’s ‘main’ routine.
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 program
file. The second assign specifies that the name A can appear in an arbitrary number of program
files. The CRE cannot determine whether to use the file C.D on volume $B1 or on volume $B2.
Effect
The CRE terminates the program.
Recovery
Correct the ASSIGNs in your TACL environment. For more details on using ASSIGNs, see the
TACL Reference Manual.
25
Ambiguity in application of ASSIGN logical_name
Cause
Your TACL environment specifies an ASSIGN such as:
ASSIGN A, $B1.C.D
but the program contains more than one logical file named A.
Effect
The CRE terminates the program.
Recovery
Correct the ASSIGNs in your TACL environment. For more details on using ASSIGNs, see the
TACL Reference Manual.
368 Run-Time Messages