Re: Date format errors creating timestamp

D, T, and Z fields are not stored in any format useful to us. For instance, as I understand it, a date field is only 4 somethings in length. These fields know what they are and we don't care what they are. We only care how we see them. In other words, QTSTAMP is not a z field so you can't slip a z field in to it. If QTSTAMP is a new field in the file, why not change the field's definition to being a timestamp field?


On 7/9/2014 11:40 AM, Dale Janus wrote:

I have an old file that contains a date in yyyymmdd and time in hhmmss as decimals. I am trying to create a time stamp field from them.

d newdate s D inz(d'2012-10-10')
d newtime s T inz(t'23.30.59')
D myts s z

c eval newdate = %date(gqtdten:*iso)
c eval newtime = %time(gqttime:*hms)
c eval myts = newdate + newtime
c
c eval qtstamp = myts




My debug calcs looks like I created the time stamp correctly, but when I go to write the record, I get CPF5035, Data mapping error on member QUOTEHIST code 17, bad date, time, timestamp.
I dumped the program and the field looks like this:

QTSTAMP TIMESTAMP(26) '2013-11-25-07.58.12.000000'
VALUE IN HEX 'F2F0F1F360F1F160F2F560F0F74BF5F84BF1F24BF0F0F0F0F0F0'X
QTSTAT CHAR(2) 'OH' 'D6C8'X
QTTIME PACKED(6,0) 075812. '0075812F'X




I can step through the program with debug, but when I go to write, I get the error on the first record

C WRITE QThREC



I thought I was doing good moving this stuff around and creating a new time stamp. it looks good to me. but something is wrong.

There is only one timestamp field, all other fields are character or decimal. The only other field is a record id. The new file is defined by DDL and contains a unique record id that I am assuming the system will generate.

---Dale