Modifying a VMSTIMESTAMP in a field

[Joe Boyle]

Ooooops, 

I have been advised that syntax ' item tt = tt + tt init ts ' should have
been ' item tt = tt + .0001 init .0001 ', for which many thanks :)

Regards, Joe.


-----Original Message-----
From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Joe Boyle
Sent: 15 August 2005 19:53
To: 'John Stires'; powerh-l at lists.sowder.com
Subject: RE: Modifying a VMSTIMESTAMP in a field

How about the following, where you decide the initial value of temp tt by
dividing 1 by the number of records that are affected ( plus )

acc date_file

select if date_field     < condition ...>

temp tt float size 8 

temp td float size 8 


item td = 20040101               << required date >>

item tt = tt + tt init .0001     << 1 / (no of recs +) >>

define dd float size 8 = date ( tt , td )

output date_file update 

item date_field final dd


P.S. are you finding that even syntax like 'define dt int * 10 = dateextract
(date_field,time ) doesn't let you see the date ?

Regards, Joe. 

________________________________________
From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
John Stires
Sent: 15 August 2005 16:12
To: powerh-l at lists.sowder.com
Subject: Modifying a VMSTIMESTAMP in a field

Due to a system problem, a number of records were not created when they
should have been created.  Now we are trying to create these
missing records for that date that have a time stamp for that day. The
value normally placed in that field is VMSTIMESTAMP which is normally never
manipulated or displayed.  When we went with the VMSTIMESTAMP value field, I
told my boss that we would never be able to look at it or manipulate it; all
it would do was to force records into a chronological order and make the
indexes unique.  To that end, we are having only minor duplicate problems
that we are handling during the batch process that creates these records.
Now, we have a number of records to create, in the hundreds, but need to
have an appropriate value for the VMSTIMESTAMP for a day in the past. We can
take another record containing a time stamp for that day. So far so good.
Then if we could increment the time component by some value, we do not care
what, so long as it ends up still for that day and we are not creating
duplicate indexed records...a bad thing to do with unique indexes.  I know
that the smallest increment coming out of a VMSTIMESTAMP is 100th of a
second, but what do I have to add to be in that ball park is the question.
Does anyone have anything in their bag of tricks that you can come up with
that may be of some help???  We are running on OpenVMS 6.2 with 7.10e6
PowerHouse with an RDB database.
Thanks for any help anyone can give.
John


-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.