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

Run-Time Diagnostic Messages
HP COBOL Manual for TNS/E Programs—520347-003
48-12
Message List
24
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 and the TACL Reference Manual.
25
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
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.
Effect. The run unit terminates abnormally.
Conflict in application of ASSIGN
program_name.logical_name
Ambiguity in application of ASSIGN
logical_name
Invalid PARAM value text ( error )
PARAM name 'value'