Re: Date format errors creating timestamp -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

uh oh...

are you saying that you get an error message when you eval timestamp to timestamp? Wow. That is odd. I totally missed that.

On 7/9/2014 1:24 PM, Dale Janus wrote:

message: 2
date: Wed, 09 Jul 2014 12:15:55 -0500
from: Booth Martin<booth@xxxxxxxxxxxx>
subject: 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?

As clear as I try to make my messages, I always leave out something.

The field QTSTAMP is a new field in the new file defined as timestamp. I ended up with the intermediate field MYTS as I was trying different things to get the code to work.

I'm not sure what you mean by D,T,Z not stored in format useful to us. How else can I create a timestamp field without using these definitions?

I am just confused because my program dump shows the timestamp field to look correct.

---Dale

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.