HP3000-L Archives

February 2005, Week 3

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
CI Variables and storing longint types in them Question
From:
Brian Donaldson <[log in to unmask]>
Reply To:
Brian Donaldson <[log in to unmask]>
Date:
Mon, 21 Feb 2005 17:13:20 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines) 
The intrinsic HPCIPUTVAR will put an integer to the variable table when you
specify item number = 1.

However, moving a PIC S9(18) COMP field (the longint field) into an
integer field (PIC S9(09) COMP) is causing the value in the variable stored
in the CI variable table to "look" suspiciously incorrect.

It certainly doesn't look correct because it contains the same value every
time I run the program.

These double integers are supposed to represent "microseconds since January
1, 1970" and so I think their value should be changing every time I run
the program.

Do I need to split my PIC S9(18) COMP value up into two separate
PIC S9(09) COMP fields and then do two separate calls to HPCIPUTVAR?

I certainly don't like that idea at all. I would prefer to store the entire
longint_type into the variable table.

Anybody got any ideas ?


TIA,
Brian.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2