SAE

SQLNAME ALREADY EXISTS

Reason:

The SQL name is not unique according to the rules for naming (see the CA Datacom/DB SQL User Guide). The type of occurrence referenced depends on the internal command being issued to CA Datacom/DB. Look in the SQLWA or in the parentheses in the error message line of the Datadictionary online Interactive SQL Service Facility Output panel for one of the following internal commands:

If the SQL command is QEXEC or QEXEI, then an occurrence already has this SQL name.
If the SQL command is QINSP (or the code is returned during a precompile, not an execution), then the problem is a PLAN occurrence. This most likely occurred because of a partial backout during the last attempt at precompiling the plan.

Action:

To obtain a list of the existing entity-occurrences, submit a Schema Report through Datadictionary batch processing or an index report (batch or online). The Datadictionary occurrence name for an occurrence created through SQL, including a plan, begins with the AUTHID.

For other than a PLAN occurrence, either assign a different SQL name or drop the existing entity-occurrence.
For a PLAN occurrence, remove the plan from Datadictionary using the online Interactive SQL Service Facility or the batch or online delete functions.

Note: If the code was returned during a Datadictionary online Interactive SQL Service Facility execution, the occurrence name of the plan is in the format authid-SQLDDxxx, where xxx is the 3-character OP-ID associated with the person signed on.