Description:
PCB-00109 Unable to open generated source file “string“
Cause:
The precompiler was unable to open the output file specified by the ONAME precompiler option. Some possible causes follow:
- The filename is misspelled.
- The file does not exist.
- The search path to the file is incorrect.
- File access privileges are insufficient.
- Another user has locked the file.
- There is not enough disk space.
- There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager).
ORADB-PCB pcb00109, unable to open generated source file
Description:
PCB-00235 Table size mismatch in INTO/USING. Minimum is: number
Cause:
The size of a table variable in an INTO/USING clause of a dynamic EXECUTE statement has been ARRAYLEN…EXECUTE’d while the other host variable has not and is not a table of dimension 1 or a plain non-table host variable. Example:
01 X PIC X(10) OCCURS 10.
01 Y PIC S9(4) COMP OCCURS 10.
01 Z PIC S9(4) COMP. ... EXEC SQL ARRAYLEN X (DIM) EXECUTE END-EXEC.
... EXEC SQL EXECUTE S1 USING :X, :Y END-EXEC. <-- error EXEC SQL
EXECUTE S1 USING :X, :Z END-EXEC. <-- ok
Please note that this error differs from 233 in that it is an error and not a warning.
ORADB-PCB array, dy, error
Description:
PCB-00402 Pseudo-text not properly terminated
Cause:
A block of pseudo-text has not been properly terminated with “==”.
ORADB-PCB
Description:
PCB-00636 This attribute is only valid for External LOB types
Cause:
A request for a LOB attribute was made in a LOB DESCRIBE statement in which the given LOB was not an External LOB type (BFILE).
ORADB-PCB
Description:
PCB-00211 VARYING not supported with PIC N or PIC G variable “string“
Cause:
The keyword VARYING was used in a PIC N variable declaration.
ORADB-PCB
Description:
PCB-00304 Oracle extension to the WHENEVER statement
Cause:
An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a nonconforming keyword such as NOTFOUND, STOP, RAISE, or DO was used in the WHENEVER statement. (Note that NOT FOUND is ANSI-compliant.) For example, the offending code might look like:
EXEC SQL WHENEVER SQLERROR STOP END-EXEC.
This informational message is issued by the FIPS Flagger when FIPS=YES.
ORADB-PCB error, not found, oracle
Description:
PCB-00554 Must include SQLCA when mode=ANSI and WHENEVER SQLWARNING used
Cause:
When MODE={ANSI | ANSI14}, an attempt was made to use the WHENEVER SQLWARNING statement without declaring the SQLCA. When MODE={ANSI | ANSI14}, declaring the SQLCA is optional, but to use the WHENEVER SQLWARNING statement, the SQLCA must be declared.
ORADB-PCB
Description:
PCB-00007 string
Cause:
This is a generic error message from the command-line processor.
ORADB-PCB error
Description:
PCB-00224 Ambiguously referenced variable “string“
Cause:
There is more than one variable of the same name and the qualification given was insufficient to determine which variable the reference was to.
ORADB-PCB cobol pcb-s-00224, oracle error pcb-s-00224, pcb-s-00224, pcb-s-00224 ambiguously reference variable, pcb-s-00224 procobol, pcb-s-00224, ambiguously, pcb-s-00224とは
Description:
PCB-00315 DECLARE TABLE is an Oracle extension
Cause:
An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the DECLARE TABLE statement was used.
ORADB-PCB oracle