Database Error Messages

Failure to generate PL/SQL statement stmt used to control TIP processing of the field fname for compiler clause clause.

Typical IBMVSCOBOLII clauses are: OCCURS (requires FOR/LOOP logic) OCCURS DEPENDING ON (requires FOR/LOOP logic) REDEFINES (requires IF/END IF logic)

This message may be preceeded by specific messages describing the error. Possible errors include disk access, invalid datatype, and/or missing nested record or field datatype definitions.

Follow recommended action for the first error message issued, and ensure the PG DD entries for the indicated parameter are correct and that disk access is alllowed to output work files.

Failure to generate PL/SQL statement stmt used to control TIP processing of the field fname for compiler clause clause.

Typical IBMVSCOBOLII clauses are: OCCURS (requires FOR/LOOP logic) OCCURS DEPENDING ON (requires FOR/LOOP logic) REDEFINES (requires IF/END IF logic)

This message may be preceeded by specific messages describing the error. Possible errors include disk access, invalid datatype, and/or missing nested record or field datatype definitions.

Follow recommended action for the first error message issued, and ensure the PG DD entries for the indicated parameter are correct and that disk access is alllowed to output work files.

Failure to generate PL/SQL statement stmt used to control TIP processing of the field fname for compiler clause clause.

Typical IBMVSCOBOLII clauses are: OCCURS (requires FOR/LOOP logic) OCCURS DEPENDING ON (requires FOR/LOOP logic) REDEFINES (requires IF/END IF logic)

This message may be preceeded by specific messages describing the error. Possible errors include disk access, invalid datatype, and/or missing nested record or field datatype definitions.

Follow recommended action for the first error message issued, and ensure the PG DD entries for the indicated parameter are correct and that disk access is alllowed to output work files.