CRE Programmer's Guide

Run-Time Diagnostic Messages

Common Run-Time Environment (CRE) Programmer’s Guide—528146-004

10-10

CRE Service Function Messages

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. See the HP Tandem

Advanced Command Language (TACL) Reference Manual for more information on

using ASSIGNs.

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. See the HP Tandem

Advanced Command Language (TACL) Reference Manual

for more information on

using ASSIGNs.

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:

PARAM DEBUG [ ON ]

[ OFF ]

The CRE reports this error if a DEBUG PARAM has a value other than ON or OFF.

error, if present, is a file-system error.

Conflict in application of ASSIGN

program_name.logical_name

Ambiguity in application of ASSIGN

logical_name

Invalid PARAM value text ( error )

PARAM name 'value'