Re: PRO-COBOL Problem. H E L P ! ! !

The easiest is to skip this exception (-1405) in the error handler you have in your PRO*COBOL program. It seems that variables with NULL-values are correctly assigned 0 or SPACES (COMP and DISPLAY-variables respectively), which is what we want.
We use MODE=ORACLE, ORACLE 7.1.4, version of precompiler I don't remember (being at home at the moment), MF-COBOL, AIX.

hage_at_telepost.no (Erik Hage)

In article <4h24hj$rop_at_inet-nntp-gw-1.us.oracle.com>, surman_at_oracle.com says...
>
>In article <4h08an$hmi_at_despina.neptune.com>, Edwin Sosa
 <esosa_at_guate.net> writes:
>|> Hello world:
>|>
>|> A friend of mine is having a problem with some PRO-COBOL programs.
 He didn't put
>|> indicator variables for some columns that accept null values and is
 getting the
>|> error "ORA-01405 fetched column value is null". The problem is that
 he has many
>|> hundreds of statements without the indicator variables and he's
 looking for a quick
>|> solution.
>|>
>|> He found some information in the Pro*COBOL Supplement manual that
 says something
>|> about setting the MODE option when precompiling, he tryed MODE=ORACLE
 and it doesn't
>|> work well, he tryed MODE=ANSI13 but it gives error in other
 statements.
>|>
>|> Does anybody knows any other solution to this problem??
>|>
>|> Any help will be welcome!
>|>
>|>
>The correct solution (documented in the 1.6 and higher manuals) is to
 use
>the option DBMS=V6. The better solution is to recode to use indicators,
>however.
Received on Fri Mar 01 1996 - 00:00:00 CET