I am using Cobol3 on a mainframe IBM.
I had changed the timestamp to current timestamp, a manually formated timestamp and low values. All errored.
I finally added a null indicator field to another date in the record. That fixed my problem.
User Profile
Collapse
-
bad timestamp / sqlcode - 180
I am reading a db2 record.
I am changing the key and doing an insert.
I am getting a error - sqlcode -180.
I have displayed the timestamp field and it looks good.
The record was stored previously. I just just trying to insert the same record out with a new account number (primary key).
I am stumped on what is wrong or what to do next. -
No activity results to display
Show More
Leave a comment: